3 subject="""comment 5"""
4 date="2022-08-19T17:01:42Z"
6 @skcin I'm very sorry that happened to you. I suppose it's not data loss,
7 but it sounds like a mess. You should be able to examine `git log` to find
8 what got imported, and run `git-annex unannex` on it, and then move it back
11 Seems like I underestimated the chance this would be a foot bomb.
12 I now think that git-annex import and the directory special remote should
13 skip over symlinks. Probably with an informative message to avoid silently
14 doing nothing in cases where users had been using them intentionally to
17 Such a check will be race prone, but that is only likely to matter if an
18 attacker is racing it to replace a file with a symlink, and as I discussed
19 in previous comments, such an attacker seems like they would be able to
20 accomplish the same thing with the write permission they must have.